followup #16400; use use -d:nimCompilerStackraceHints in more places #18282
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
followup #16400
this helped me a lot to reduce the bug in #18278 (original failure was from complicated code in nimterop in which stacktrace contained no useful hint as to where it originated from in user code).
The design I'm following is to add
setFrameMsg
in key places in the compiler that are often visited, which increases chances we find the relevant location in user code.with
--stacktrace:on --stacktracemsgs -d:nimCompilerStackraceHints
:before PR
after PR